The Juniper perimeter router must not be configured to be a Border Gateway Protocol (BGP) peer to an alternate gateway service provider.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-253990 | JUEX-RT-000180 | SV-253990r844003_rule | High |
| Description |
|---|
| ISPs use BGP to share route information with other autonomous systems (i.e., other ISPs and corporate networks). If the perimeter router was configured to BGP peer with an ISP, NIPRNet routes could be advertised to the ISP; thereby creating a backdoor connection from the internet to the NIPRNet. |
| STIG | Date |
|---|---|
| Juniper EX Series Switches Router Security Technical Implementation Guide | 2023-03-23 |
Details
| Check Text ( C-57442r844001_chk ) |
|---|
| This requirement is not applicable for the DODIN Backbone. Review the configuration of the router connecting to the alternate gateway. Review the [edit protocols bgp] hierarchy and verify there are no BGP neighbors configured to the remote AS that belongs to the alternate gateway service provider. For example: [edit protocols bgp] group eBGP { type external; peer-as 2; neighbor } neighbor } } Note: Neither neighbor can belong to a peer AS belonging to the alternate gateway service provider. Verify static routing to the peer AS belonging to the alternate gateway service provider. For example: [edit routing-options] rib inet6.0 { static { route } } static { route } If there are BGP neighbors connecting the remote AS of the alternate gateway service provider, this is a finding. |
| Fix Text (F-57393r844002_fix) |
|---|
| This requirement is not applicable for the DODIN Backbone. Remove BGP neighbors belonging to the alternate gateway service provider. delete protocols bgp group Configure a static route on the perimeter router to reach the AS of a router connecting to an alternate gateway. set routing-options rib inet6.0 static route set routing-options static route |